Local and remote video-camera control

ABSTRACT

This application describes techniques for controlling an apparatus that includes a camera both locally and remotely. The camera apparatuses described herein may include obfuscation components that function to selectively obfuscate a view of the camera at the request of a user. For instance, one particular camera apparatus may include a lens cap and an actuator to move the lens cap from a position in which the lens cap at least partially obfuscates the view of the camera to a position in which the lens cap does not (and vice versa). The camera apparatus may include a physical control to allow a user to locally request to open or close the lens cap, and may also include a network interface to communicate with a user device, thus allowing a user to remotely request to open or close the lens cap.

BACKGROUND

Homes are becoming more wired and connected with the proliferation ofcomputing devices such as desktops, tablets, entertainment systems,portable communication devices, speech-enabled devices, camera-baseddevices, and the like. As these computing devices evolve, many differentways have been introduced to allow users to interact with computingdevices, such as through mechanical devices (e.g., keyboards, mice,etc.), touch screens, motion, and gesture. In some instances, users maydesire flexibility in controlling these devices, while still maintainingsecurity of these devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical components or features.

FIG. 1 is a schematic diagram of an environment that includes a cameraapparatus configured to acquire video of the environment. The cameraapparatus includes a camera, a lens cap (or other obfuscationcomponent), and a physical control that is selectable to move the lenscap from a position that obfuscates a view of the camera to a positionthat does not (and vice versa). In some instances, the camera apparatusalso includes a network interface for communicating with user devices toreceive requests to open or close the lens cap. In some instances, thecamera apparatus is configured to allow users to open the lens cap whena request is received over a personal area network (PAN) (e.g.,Bluetooth, Zigbee, etc.) while not allowing users to open the lens capover a wide area network (WAN) (e.g., “over the cloud”).

FIG. 2A illustrates an example flow of a user selecting the physicalcontrol of the camera apparatus of FIG. 1 and, in response, the lens capmoving from the position in which the lens cap is not obfuscating theview of the camera to the position in which it does obfuscate this view.

FIG. 2B illustrates an example flow of a user device issuing a requestover a network to move the lens cap from the position in which the lenscap is not obfuscating the view of the camera to the position in whichit does obfuscate this view. In some instances, the camera apparatus mayallow a camera to be “opened” when the request is issued over a PAN(i.e., a short-range wireless communication channel).

FIG. 3A illustrates an example flow of a user selecting an additionalphysical control of the camera apparatus of FIG. 1 to request to mute amicrophone of the apparatus. In response, a speaker of the cameraapparatus outputs sound (e.g., white noise) to effectively “mute” themicrophone by rendering other sound from the environment (e.g., userspeech) unintelligible in any audio signal generated by the microphone.

FIG. 3B illustrates an example flow of a user issuing a request over anetwork to effectively mute the microphone by outputting the white noisefrom the speaker.

FIG. 4 illustrates a flow diagram of an example process for openingand/or closing a lens cap of a camera via a physical control on theapparatus or via a request issued over a network.

FIG. 5 illustrates a flow diagram of an example process for obfuscatinga view of a camera and muting a microphone.

DETAILED DESCRIPTION

Techniques for controlling an apparatus that includes a camera bothlocally and remotely are described herein. As described above, home,offices, and other environments often include an array of computingdevices, including those that include cameras, such as security cameras,web cameras, and the like. The camera apparatuses described herein mayinclude one or more obfuscation components that function to selectivelyobfuscate a view of the camera at the request of a user. For instance,one particular camera apparatus may include a lens cap and an actuatorto move the lens cap from a position in which the lens cap at leastpartially obfuscates the view of the camera to a position in which thelens cap does not (and vice versa).

To allow the user to control the lens cap of the camera in this manner,the camera apparatus may include a physical control that is selectableby a user to cause the actuator to move the lens cap between the openand closed positions. The physical control may comprise a push button, atoggle switch, a touch screen, or any other type of physical control.Furthermore, the camera apparatus may include a network interface forcommunicating with other devices, such as mobile devices of a user,other appliances within the environment of the camera apparatus, and/orthe like. In some instances, a user device (e.g., a mobile phone, atable device, etc.) may include a companion application for interactingwith the camera apparatus. A user may use this application to issue arequest to open and/or close the lens cap.

For instance, when a user device couples to the camera apparatus via apersonal area network (PAN), such as Bluetooth, Zigbee, Z-Wave, or thelike, the user may operate her companion application on her device toissue a request to open or close the camera. For instance, when the userreturns home from work, she may wish to close her camera given that sheno longer feels the need for a security feed. Or, when the user returnshome from work, she may wish to open her camera to engage in a videocall or the like. In either instance, the device of the user may issuethe request to the camera apparatus, which may receive the request andopen or close the lens cap as appropriate.

In other instances, the user device may communicate with the cameraapparatus over a wide area network (WAN), such as the Internet, acellular network, or the like. For instance, when the user is at work,she may wish to open her camera to view the current state of her home.Or, the user may wish to close the camera. In either instance, the usermay issue this request via her companion application and, in response,the camera may open or close the lens cap as appropriate.

In some instances, however, for security reasons the camera apparatusmay be configured to respond to requests issued over PANs but not WANs(or vice versa). For instance, in some instances the camera apparatusmay open or close the lens cap as requested when the request is receivedover Bluetooth, Zigbee, or the like, meaning that the requesting user isproximate to the camera apparatus (e.g., within meters of the cameraapparatus). Conversely, when the user device makes such a request “overthe cloud”, the camera apparatus may refrain from performing theoperation, thus lessening the risk that a nefarious user may remotelyattempt to control the camera apparatus without the permission of theowner of the camera apparatus.

In still other instances, the camera apparatus may be configured toaccept or deny request based both on the network over which the requestis received and the nature of the request itself. For instance, thecamera apparatus may allow a user device to close the lens cap whencommunicating with the camera apparatus over a WAN, while not allowingthe user to open the lens cap when communicating with the cameraapparatus over the WAN. Further, the camera apparatus may allow the userdevice to both open and close the lens cap when communicating with thecamera apparatus over a PAN. Still further, the physical control that isadjacent to the camera on a housing of the camera apparatus may be usedto both open and close the lens cap.

In some instances, the camera apparatus may receive a request to open orclose the obfuscation component from devices that are local within theenvironment of the camera apparatus. For instance, when coupled oradjacent to a building, upon a door lock of a door of the building beingunlocked, the door lock may send a request over a PAN (i.e., ashort-range wireless communication channel) to the camera apparatus toopen or close the obfuscation component. In some instance, the cameraapparatus may permit these requests when they are received from thelocal devices. Further, in some instances the camera apparatus maypermit these requests when they are received from these local devicesand when they specify a particular one of opening or closing theobfuscation component. For example, the camera apparatus may open theobfuscation component in response to receiving a request to do so fromthe door lock or other local device, while denying such a request fromthe door lock or other local device to close the obfuscation component.Of course, in some instances the converse may be true. Further, in someexamples the camera apparatus may comply with a request of the door lockor other local device regardless of the nature of the request.

In the above example, the door lock may additionally or alternativelysend a request to begin or cease recording. That is, rather than or inaddition to sending a request to open or close the obfuscationcomponent, the door lock may be configured to issue a request to thecamera apparatus to begin (or cease) recording. In one example, when adoor lock is unlocked, the door lock sends an indication of this actionto the camera apparatus and, in response, the camera apparatus ceasesits recording. In some instances the converse may be true, as the cameraapparatus may begin recording in response to receiving this indicationfrom the door lock. In another example, when the door lock is changed toan unlocked state, the door lock may send an indication of the lockingaction to the camera apparatus. In response, the camera apparatus beginsrecording. In another example, when the door lock is changed to theunlocked state, however, the camera apparatus ceases recording.

In some instances, a particular door lock may be associated with aparticular camera apparatus such that the particular camera beginsrecording upon locking or unlocking of the particular door lock, ratherthan another camera or another door. To do so, the camera apparatus or aremote device (e.g., a server accessible via a network) may store anassociation between an identifier of the particular camera apparatus andan identifier of the particular door lock, along with particularinstructions regarding actions taken by the particular camera apparatusin response to different state changes of the door lock. For instance,the camera apparatus or the remote device may store an indication thatthe particular camera apparatus is to begin recording (including openingthe obfuscation component) when the door lock transitions from a lockedstate to an unlocked state (or vice versa). Alternatively, the cameraapparatus or the remote device may store an indication that theparticular camera apparatus is to begin recording (including opening theobfuscation component) when the door lock transitions from the lockedstate to the unlocked when the door lock is activated locally via a PANas opposed to remotely over a WAN (or vice versa). That is, in instanceswhere the door lock is controllable both via short-range wirelesscommunication channels and over a WAN, the camera apparatus may beconfigured to execute differently depending on the nature of theoperation of the door lock.

Furthermore, while the above-referenced example describes a door lockissuing a request over a PAN to the camera apparatus, in some instancesother devices within the environment may issues these requests. Forinstance, when a motion sensor detects motion within an environment ofthe camera apparatus, the motion sensor may provide an indication ofthis motion to the camera apparatus either directly or via anotherdevice. In response to receiving this indication, the camera apparatusmay open its obfuscation component and/or begin recording. Of course, insome instances, the opposite may occur.

In another example a mobile device executing a particular applicationmay send, to the camera apparatus directly or indirectly, a request toopen (or close) the obfuscation component and/or a request to begin (orcease) recording of the environment by the camera apparatus. Forinstance, a delivery person dropping a package off at a residence of auser may carry a mobile device executing an application configured tocommunicate, via an interface of the mobile device, with the cameraapparatus at the residence or with a local device such as a door lock.In response to receiving an indication of the presence of the mobiledevice over a short-range wireless communication channel, the cameraapparatus may open (or close) the obfuscation component and/or may begin(or cease) recording. In one specific example, a door lock may beconfigured to transition from a locked state to an unlocked state inresponse to detecting a particular communication, such as an indicationof the presence of the mobile device of the delivery person in the aboveexample. The door lock may also, in response, send an indication over aPAN to the camera apparatus may open (or close) the obfuscationcomponent and/or may begin (or cease) recording. When the door lockceases to receiving the indication of the presence of the mobile deviceof the delivery person, the door lock may send an indication to thecamera apparatus, which may alter its state (e.g., to cease recordingand close the obfuscation component), and the door lock may alsotransition from the unlocked state back to the locked state. While oneexample is given, it is to be appreciated that the camera apparatus maychange its state in response to receiving a communication from any otherlocal device over a PAN.

In some instances, while the camera apparatus may not allow a device toopen the lens cap when communicating over a WAN, the camera apparatusmay provide video to an authenticated device making a request for videoover the WAN. For instance, a user device may execute an applicationthat allows a user to view video generated by the camera apparatus whenthe user is authenticated. For instance, the user may need to sign inwith the application via a username/password combination, biometricinformation (e.g., thumbprint data, etc.), or the like. After doing so,the user may issue requests to receive video generated by the cameraapparatus via any network, including a PAN and a WAN. In response toreceiving these requests, the camera apparatus may send the video overthe appropriate network given that the device/user is authenticated asdiscussed above. However, in some instances the user might still beunable to open the lens cap when communicating over the WAN. Therefore,the camera apparatus may provide video to the requesting user deviceregardless of the state of the lens cap (open or closed), while notallowing the user device to change the state of the obfuscationcomponent over the WAN.

In some instances, the camera apparatus may include a sensor to detectwhen the lens cap is unable to be closed, such as due to the existenceof a foreign object (e.g., a child's finger) in the path of travel ofthe lens cap. In response to making this determination, the cameraapparatus may send an indication that the lens cap has been unable toclose (or open) to a user device that issued the request, ifappropriate. Further, if the request originated from a user device, thecamera apparatus may send one or more images (e.g., a video feed or astill image) to the user device that sent the request. This sensor maycomprise a pressure sensor that detects when the lens cap is subject topressure greater than a threshold. In response to detecting this amountpressure, the actuator may retract the lens cap and send the indicationto the user device if appropriate. In another example, the sensor maycomprise a laser aligned with a receiving camera. If the camera isunable to detect the laser at any point during the movement of the lenscap—indicating the presence of a foreign object in the path oftravel—the lens cap may retract an indication may be sent ifappropriate.

While the above example describes a lens cap, the camera apparatusesdescribed herein may utilize other types of obfuscation components. Forinstance, a camera may include a light-source (e.g., an LED) within thecamera or outside of the camera that obfuscates the camera byeffectively blinding the camera (e.g., overexposing the camera's imagesensor to light input). For instance, the light-source may be configuredto emit light substantially parallel to an optical axis of the camera,thus preventing the camera from capturing image of the environment. Insome instances, this light-source may emit light outwards towards theenvironment, while in other instances the light-source may emit thelight away from the environment (i.e., “into” the camera). In eitherinstance, the light may effectively blind the camera and may be visibleto a user within the environment, thereby assuring the user that theview of the camera has been obfuscated.

In another example, the camera may include a lightguide configured todisseminate light for blinding the camera. For instance, the lightguidemay comprise a transparent lens that resides within the optical path ofthe camera. The lightguide may include grating elements that function todisperse light when light is received from an edge of the lightguide(perpendicular to the optical axis of the camera). Therefore, theobfuscation component may comprise the lightguide and a light-sourcealong an edge of the lightguide, such that when the user requests toobfuscate the view of the camera the light-source is illuminated. Thislight is emitted towards the lightguide, which disseminates the lightsubstantially in the direction of the camera, thus effectively blindingthe camera.

In still other instances, the obfuscation component may comprise acolored lens or the like that is insertable within the optical path ofthe camera. When the user requests to obfuscate the view of the camera,an actuator may move the colored lens from a position in which it doesnot reside within the optical path into a position in which it does.This colored lens may reside within the camera or outside of the camera,similar to a lens cap. Further, because of the color of the lens, whenthe lens resides within the optical path of the camera, the user mayreceive assurance that the view of the camera is being obfuscated.

In still other instances, the camera apparatus may include a microphonefor capturing audio from the environment of the apparatus, as well as aspeaker for outputting audio within the environment. In these instances,a user within the environment may be able to use the apparatus toconduct voice communications with remote users, such as a user executingthe companion application on her user device. That is, the cameraapparatus may send audio signals generated using the microphone to thecompanion application, which may in turn send generated audio signalsfor output on the speaker of the camera apparatus within theenvironment. In addition, the camera apparatus may send video of theenvironment to the companion application.

In some instances, however, a user may wish to effectively “mute” themicrophone. Again, the user may issue such a request via a physicalcontrol on the apparatus and/or over a network from a user device (e.g.,via the companion application). In response to receiving a request tomute the microphone, the camera apparatus may send an instruction to thespeaker to output sound, such as white noise, such that other sound fromthe environment, such as user speech, is unintelligible from any audiosignal generated by the microphone. Further, the white noise may beperceptible to the human ear such that the user within the environmentreceives assurance that the microphone has been effectively muted. Asabove, the apparatus may allow a user to mute (or un-mute) themicrophone via a physical control of the apparatus or via a PAN, whilenot allowing the user to do so over a WAN. In some instances, theapparatus may allow user devices to mute the microphone over a WAN whilenot allowing user devices to un-mute the microphone over the WAN.

FIG. 1 is a schematic diagram of an environment 102 that includes acamera apparatus 104 that includes a camera 106 configured to acquirevideo of the environment 102. In addition, the camera apparatus includesan obfuscation component 108 that is able to selectively obfuscate aview of the camera. As described above, the obfuscation component 108may comprise a lens cap that is able to move between open and closedpositions, a light-source configured to blind the camera 106, alight-source and a lightguide, or any other component capable ofinterfering with the video acquisition by the camera 106. In instanceswhere the obfuscation component 108 comprises a physical covering, suchas lens cap or colored lens, this component may include or couple withan actuator to mechanically move the physical covering into place.

In some instances, a user 110(1) within the environment 102 and/or auser 110(2) outside of the environment may request to obfuscate or ceaseobfuscating the view of the camera 106. These requests may be requestedboth locally and remotely in some instances. As illustrated, the cameraapparatus 104 may include one or more physical controls 112 that, whenselected, cause the obfuscation component to begin obfuscating or ceaseobfuscating the view of the camera. For instance, the physical control112 may comprise a push button, a toggle switch, a touch screen, or thelike.

In addition, a user may issue a request to obfuscate and/or ceaseobfuscating the view of the camera using a respective device 114(1) or114(2) of the user. As illustrated, each user device includes respectiveprocessor(s) 116(1) or 116(2), network interfaces 118(1) or 118(2),memory 120(1) or 120(2), and a companion application 122(1) or 122(2)stored in the memory and executing on the processors. As such, each ofthe users may utilize their respective user devices to issue requestsvia their respective companion applications.

Each of the network interfaces 118(1) and 118(2) may include a personalarea network (PAN) component to enable communications over one or moreshort-range wireless communication channels. For instance, the PANcomponent may enable communications compliant with at least one of thefollowing standards IEEE 802.15.4 (ZigBee), IEEE 802.15.1 (Bluetooth),IEEE 802.11 (WiFi), or any other PAN communication protocol.Furthermore, each of the network interfaces 118(1) and 118(2) mayinclude a wide area network (WAN) component to enable communication overa wide area network.

The stated IEEE 802.15.4 is intended to provide fundamental lowernetwork layers of a type of wireless personal area network (WPAN) thatis relatively low-cost, low-speed and ubiquitous between devices. Thisstandard may offer less bandwidth and require less power than otherstandards. This standard is focused on very low cost communication ofnearby devices with little to no underlying infrastructure, to takefurther advantage of its lower power consumption. This standard maygenerally provide a 10-meter communications range with a transfer rateof approximately 250 kbit/s in some instances.

The IEEE 802.15.1 standard, meanwhile, is another wireless technologystandard for exchanging data over short distances (usingshort-wavelength UHF radio waves in the ISM band from 2.4 to 2.485 GHz)from fixed and mobile devices, and building personal area networks(PANs). The IEEE 802.11 standard, meanwhile, is a set of media accesscontrol (MAC) and physical layer (PHY) specifications for implementingwireless local area network (WLAN) computer communication in the 900 MHzand 2.4, 3.6, 5, and 60 GHz frequency bands. Of course, while a fewexamples have been introduced, it is to be appreciated that otherimplementations may implement other wireless-communication standards.

As illustrated, the camera apparatus 104 further includes networkinterface(s) 124, processor(s) 126, and memory 130, which stores acontroller 130 that is configured to issue instructions to theobfuscation component 108 to obfuscate or cease obfuscating the view ofthe camera 106. The camera apparatus 104 may further include one or moremicrophones 132 and one or more speakers 134 as described below.

As used herein, a processor may include multiple processors and/or aprocessor having multiple cores. Further, the processors may compriseone or more cores of different types. For example, the processors 404may include application processor units, graphic processing units, andso forth. In one implementation, the processor 404 may comprise amicrocontroller. The microphones 132, meanwhile, may comprise anacoustic-to-electric transducer or sensor that converse sound from theenvironment into an electrical signal, while the speakers 134 maycomprise one or more electroacoustic transducers that convert electricalaudio signals into corresponding sounds for output in the environment.

The memory 128, as well as each memory described herein, may includevolatile and nonvolatile memory, removable and non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules, orother data. Such memory includes, but is not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,RAID storage systems, or any other medium which can be used to store thedesired information and which can be accessed by a computing device. Thememory 116 may be implemented as computer-readable storage media(“CRSM”), which may be any available physical media accessible by theprocessor(s) 126 to execute instructions stored on the memory 128. Inone basic implementation, CRSM may include random access memory (“RAM”)and Flash memory. In other implementations, CRSM may include, but is notlimited to, read-only memory (“ROM”), electrically erasable programmableread-only memory (“EEPROM”), or any other tangible medium which can beused to store the desired information and which can be accessed by theprocessor(s) 126.

Further, functional modules are shown stored in the respective memories,the same functionality may alternatively be implemented in hardware,firmware, application specific integrated circuits, field programmablegate arrays, or as a system on a chip (SoC). In addition, while notillustrated, each respective memory discussed herein may include atleast one operating system (OS) module that is configured to managehardware resource devices such as the interfaces 118(2) and 124, the I/Odevices of the respective apparatuses, and so forth, and provide variousservices to applications or modules executing on the processors. Such OSmodule may implement a variant of the FreeBSD™ operating system aspromulgated by the FreeBSD Project; other UNIX™ or UNIX-like variants; avariation of the Linux™ operating system as promulgated by LinusTorvalds; the Windows® operating system from Microsoft Corporation ofRedmond, Wash., USA; LynxOS as promulgated by Lynx SoftwareTechnologies, Inc. of San Jose, Calif.; Operating System Embedded (EneaOSE) as promulgated by ENEA AB of Sweden; and so forth

In some instances, the camera apparatus 104 is configured to allow usersto open the lens cap when a request is received over a personal areanetwork (PAN) (e.g., Bluetooth, Zigbee, etc.) while not allowing usersto open the lens cap over a wide area network (WAN) (e.g., “over thecloud”), such as illustrated network 136. For instance, the user 110(1)may issue a request to obfuscate or cease obfuscating the view of thecamera using the physical control 112 residing on the apparatus 104.Additionally or alternatively, the user 110(1) may pair his device114(1) with the apparatus over a PAN and may issue a request toobfuscate or cease obfuscating the camera 106 over the PAN using thecompanion application 122(1). In response to receiving this request, thecamera apparatus 104 may determine that the request originated from adevice coupled to the apparatus over a PAN and, therefore, may issue aninstruction in accordance with the received request to the obfuscationcomponent 108. Further, while FIG. 1 illustrates a user operating a userdevice 114(1) to issue this request, in some instances another device,such as a smart appliance, within the environment may issue thisrequest. For instance, a door lock or door sensor having the capabilityof communicating with the apparatus 104 over a PAN may issue a requestto the apparatus in response to the door lock being unlocked or the doorsensor detecting the opening of the door.

In other instances, meanwhile, the user 110(2) may issue a request toobfuscate or cease obfuscating the camera 106 using the companionapplication 122(2) executing on the user device 114(2). In this example,the device 114(2) couples to the apparatus 104 over the network 136. Thenetwork 136 may generally represent a WAN that comprises an array orwired networks, wireless networks (e.g., WiFi), or combinations thereof.In response to receiving the request from the device 114(2), theapparatus 104 may determine that the request has been received over theWAN network 136. In some instances, the apparatus 104 may accordinglydeny the request and may send an indication of this denial to the userdevice 114(2). In other instances, in response to making thisdetermination the apparatus 104 may send a request for authenticationinformation to the user device 114(2). For instance, in response arequest being received over a WAN, the apparatus 104 may request that auser provide a personal identification number (PIN), username/password,biometric information, or any other type of authentication information.If the user is authenticated, the apparatus 104 may perform the request.In still other instances, the apparatus 104 may be configured to performcertain requests received over a WAN but not others. For example, theapparatus 104 may execute a request over the WAN to obfuscate the camera106 while not executing a request over the WAN to cease obfuscating thecamera (or vice versa).

FIG. 2A illustrates an example flow of a user selecting a first physicalcontrol 112(1) of the camera apparatus 104 and, in response, theobfuscation component 108 beginning to obfuscate the camera 106. In thisexample, the obfuscation component 108 comprises a lens cap that isconfigured to mechanically move, via an actuator, from an open positionto a closed position (and vice versa).

At 202(1), the user is shown selecting the physical control 112(1) whilethe lens cap is in the open position. The physical control 112(1) maycomprise any kind of mechanical or digital control configured togenerating and sending a control signal to the actuator to cause theactuator to close the lens cap. For instance, the physical control maycomprise a depressible button, a toggle switch, a rotatable knob, atouchscreen control, or the like.

In response to the user selecting the physical control 112(1), at 202(2)the lens cap is shown being swiveled by the actuator from the openposition to the closed position. The actuator may comprise any sort ofcomponent configured to control movement of the lens cap from the openposition to the closed position and back. For instance, the actuator maycomprise a mechanical actuator (e.g. spring-loaded, etc.), a hydraulicactuator, a pneumatic actuator, an electric actuator, a thermal ormagnetic actuator, or the like. At 202(3), the lens cap is shown in theclosed position, obfuscating the view of the camera 106. As such, theuser has been able to close the lens cap via selection of the physicalcontrol 112(1) that is on a common housing as the camera 106. Further,the user may request to cease obfuscation of the camera 106 via asubsequent selection of the physical control 112(1).

FIG. 2B illustrates an example flow of a user device issuing a requestover a network to move the lens cap from the position in which the lenscap is not obfuscating the view of the camera 106 to the position inwhich it does obfuscate this view. In some instances, the cameraapparatus 104 may allow the camera 106 to be “opened” when the requestis issued over a PAN (i.e., a short-range wireless communicationchannel), while not when the request is issued over a WAN. In eitherinstance, the illustrated user device may execute an application that isconfigured to send the request to close (or open) the lens cap. The usermake a selection to close (or open) the lens cap via the applicationand, in response, the device may send a corresponding request to thecamera apparatus via a network interface on the device. In otherinstances, the request to close (or open) the lens cap may originatefrom another device within the environment of the camera apparatus asdiscussed above, such as a door lock, a motion sensor, or the like.

At 204(1), the user utilizes the companion application executing on theuser device to issue a request to close the lens cap at a time when thelens cap is in an open position. At 204(2), the camera apparatus 104 hasreceived the request and has begun closing the lens cap. In thisexample, the user device is local to the camera apparatus and the sendsthe request to the camera apparatus via a PAN (i.e., a short-rangewireless communication channel). At 204(3), the lens cap has moved tothe closed position. In some instances, the camera apparatus 104 maymove the lens cap back to the open position in response to receivinganother request from the user device.

FIG. 3A illustrates an example flow of a user selecting an additionalphysical control 112(2) of the camera apparatus 104 to request to mutethe microphone 132 of the apparatus 104. Again, the physical control112(2) may comprise any kind of mechanical or digital control configuredto generating and sending a control signal to the actuator to cause theactuator to close the lens cap. For instance, the physical control maycomprise a depressible button, a toggle switch, a rotatable knob, atouchscreen control, or the like.

At 302(1), the user selects the physical control 112(2). At 302(2), inresponse, the speaker 134 of the camera apparatus 104 outputs sound(e.g., white noise) to effectively “mute” the microphone 132 byrendering other sound from the environment (e.g., user speech)unintelligible in any audio signal generated by the microphone. That is,in response to receiving a control signal generated in response to theuser selecting the physical control 112(2) at 302(1), the speakergenerates audio using a predefined audio signal, with the audiopotentially comprising white noise for the purpose of masking any audiocaptured by the microphone of the camera apparatus. That is, bygenerating audio immediately adjacent to the microphone using thespeaker, the camera apparatus lessens the likelihood that any audiosignal generated at that time by the microphone will includeintelligible conversation of users in the environment or other sounds.

FIG. 3B illustrates an example flow of the user issuing the request tomute the microphone over a network. In some instances, the cameraapparatus 104 may allow the microphone 132 to be “muted” when therequest is issued over a PAN (i.e., a short-range wireless communicationchannel), while not when the request is issued over a WAN (or viceversa). In either instance, the illustrated user device may execute anapplication that is configured to send the request to mute (or un-mute)the microphone 132. The user make a selection to mute (or un-mute) themicrophone via the application and, in response, the device may send acorresponding request to the camera apparatus via a network interface onthe device. In other instances, the request to mute (or un-mute) themicrophone may originate from another device within the environment ofthe camera apparatus as discussed above, such as a door lock, a motionsensor, or the like.

At 304(1), the user operates his user device to send the request to thecamera apparatus 104. At 304(2), and in response, the speaker 134 of thecamera apparatus 104 outputs sound (e.g., white noise) to effectively“mute” the microphone 132 by rendering other sound from the environmentunintelligible in any audio signal generated by the microphone.

FIG. 4 illustrates a flow diagram of an example process 400 for openingand/or closing a lens cap of a camera via a physical control on theapparatus or via a request issued over a network. This process (as wellas each process described herein) is illustrated as a logical flowgraph, each operation of which represents a sequence of operations thatcan be implemented in hardware, software, or a combination thereof. Inthe context of software, the operations represent computer-executableinstructions stored on one or more non-transitory computer-readablestorage media that, when executed by one or more processors, perform therecited operations. Generally, computer-executable instructions includeroutines, programs, objects, components, data structures, and the likethat perform particular functions or implement particular abstract datatypes. The order in which the operations are described is not intendedto be construed as a limitation, and any number of the describedoperations can be combined in any order and/or in parallel to implementthe process. In some instances, the operations performed in theprocesses 400 and 500 are performed by the controller 130.

At 402, the controller 130 receives a request to open or close anobfuscation component, such as a lens cap, colored lens, or the like, toobfuscate a view of a camera. For instance, the controller 130 mayreceive this request in response to a user selecting one of the physicalcontrols above. The physical controls may comprise mechanical and/ordigital controls. Alternatively, the controller 130 may receive therequest over the network and via a network interface of the device onwhich the controller executes.

At 404, the controller 130 determines whether the request is receivedvia a physical control or over a network. In some instances, a selectionof a physical control may result in a request routed to the controller130 in a manner that differs from the a request routed to the controllervia the network interface of the device. Additionally or alternatively,a request received over the network may include header information orother types of information indicating that the request was set from aremote device, which a request originating via selection of a physicalcontrol at the device on which the controller 130 executes may lack.

In response to determining that the request is received via a physicalcontrol, at 406 the controller 130 determines whether the request is toopen the obfuscation component or close the obfuscation component. Forinstance, the controller 130 may determine the current position of theobfuscation component and may interpret the request as a request tochange the state of the obfuscation component to the opposite state.Additionally or alternatively, the request may include payloadinformation specifying whether the obfuscation component is to be openedor closed.

In the instances where the request is determined to be a request to openthe obfuscation component, at 408 the controller issues an instructionto the actuator of the obfuscation component to open the obfuscationcomponent. That is, the controller 130 may issue a control signal thatis executable by the actuator to open the obfuscation component. Thismay include instructing a mechanical actuator to close a lens cap.

In the instances where the request is determined to be a request toclose the obfuscation component, at 410 the controller 130 issues aninstruction to the actuator to close obfuscation component. That is, thecontroller 130 may issue a control signal that is executable by theactuator to close the obfuscation component. This may includeinstructing a mechanical actuator to close a lens cap. As the readerwill appreciate, in this example the user is able to both open and closethe obfuscation component when the user operates the obfuscationcomponent via the physical control, given that the user in the sameenvironment as the camera apparatus.

If, however, the controller 130 determines that the request is receivedover a network, at 412 the controller 130 determines whether the requestis to open or close the obfuscation component. Again, the controller 130may determine the current position of the obfuscation component and mayinterpret the request as a request to change the state of theobfuscation component to the opposite state. Additionally oralternatively, the request may include payload information specifyingwhether the obfuscation component is to be opened or closed.

If the latter, then at 414 the controller 130 may issue an instructionto the actuator to close the obfuscation component, regardless of thetype of network over which the request is received. This may includesending a control signal to a mechanical, hydraulic, pneumatic, or othertype of actuator instructing the actuator to physically move theobfuscation component to a closed position.

If, however, the request is to open the obfuscation component, then at416 the controller may determine whether the network over which therequest is received is a PAN or a WAN. For instance, the controller 130may determine whether a PAN component received the request or whetherthe request was received via a WAN component. In another example, thecontroller 130 may analyze header or payload information associated withthe request to determine whether the request was received by the cameraapparatus via a PAN or via a WAN.

If the former instances, meaning that the device that sent the requestis local to the camera apparatus, then at 418 the controller 130 mayissue an instruction to the actuator to open the obfuscation component.Again, this may include sending a control signal to a mechanical,hydraulic, pneumatic, or other type of actuator instructing the actuatorto physically move the obfuscation component to an open position If thelatter, however, then at 420(1) the controller may deny the request toopen the obfuscation component (given that the device is not local tothe camera apparatus). That is, the camera apparatus may refrain fromissuing the afore-mentioned control signal to open the obfuscationscomponent.

In other instances, meanwhile, at 420(2) the controller 130 may insteadrequest authentication information, such as PIN, from the user devicethat sent the request over the WAN. For instance, the camera apparatusmay send, over the work, data to the device that sent the request, thedata for rendering a user interface (UI) that requests and is configuredto receive authentication information from the user of the device thatsent the request. If the user device provides, to the camera apparatusin response to the rendering of the UI, appropriate authenticationinformation, then the controller 130 may proceed to open the obfuscationcomponent. That is, the controller 130 may send the appropriate controlsignal instructing the actuator to move the obfuscation component to theopen position. Of course, while FIG. 4 illustrates one particularexample, in other instances, the controller 130 might not open or closethe obfuscation component when a request is received over a WAN. Or, thecontroller 130 may open or close the obfuscation component withoutregard to the type of network over which a request is received.

FIG. 5 illustrates a flow diagram of an example process 500 forobfuscating a view of a camera and muting a microphone. Again, thecontroller 130 may perform some or all of the process 500 in someinstances. At 502, the controller 130 receives an indication that aphysical control of a camera apparatus has been selected at a time whena lens cap of the camera apparatus resides in an open position. In someinstances, a selection of a physical control may result in a requestrouted to the controller 130 in a manner that differs from the a requestrouted to the controller via the network interface of the device, thusallowing the controller 130 to accurately identify the genesis of therequest. Additionally or alternatively, a request received over thenetwork may include header information or other types of informationindicating that the request was set from a remote device, which arequest originating via selection of a physical control at the device onwhich the controller 130 executes may lack.

At 504, the controller 130 sends a first instruction to an actuator ofthe camera apparatus to move the lens cap from the open position to theclosed position. For instance, the controller 130 may issue a controlsignal that is executable by the actuator to move the lens cap from anopen to a closed position.

At 506, the camera apparatus receives, over a network, a signal from aremote device requesting to move the lens cap to the open position. At508, the controller 130 determines in this example that the signal isreceived over a PAN. For instance, the controller 130 may determine thata short-range wireless interface received the request rather than awide-area-network interface. In another example, the controller 130 mayanalyze header or payload information associated with the request todetermine that the request was received by the camera apparatus via aPAN rather than a WAN.

At 510, and in response, the controller 130 proceeds to send a secondinstruction to the actuator to move the lens cap to the open position.Again, the controller 130 may issue a control signal that is executableby the actuator to move the lens cap from the closed to the openposition. In response to receiving this control signal, the actuator maymechanically, pneumatically, hydraulically, or in any other manner movethe lens to the open position.

Sometime thereafter, the controller 130 may receive a request to againmove the lens cap to the closed position. In this example, the requestis received from a user device over a network. In either instance, at512 the controller may 130 receive an indication, from a sensor of thecamera apparatus, that the lens is unable to close. For instance, apressure sensor may send an indication that it has detected pressurethat is greater than a threshold pressure, or a laser sensor may send anindication that a optical path of the laser is inhibited, thuspresenting the potential that an object is within the path of closure ofthe lens.

At 514, in response the controller 130 may send at least one image tothe user device that issued the request to close the lens cap. Forinstance, the controller 130 may send a video captured by the camera,thus allowing the user to see what it is that is keeping the lens capfrom moving to the closed position. That is, the controller may causevideo or a still image captured by the camera to be send, over thenetwork, to the device from the request originated.

At 516, meanwhile, the controller 516 receives a request, via a physicalcontrol or from a user device over a network, to mute a microphone ofthe device. Again, the controller 130 may receive an indication that aphysical control present on the actual apparatus has been selected. At518, and in response, the controller 130 sends a third instruction to aspeaker of the apparatus to cause the speaker to output white noise,thus rendering other sound from the environment of the apparatusunintelligible from any audio signal generated by the microphone of theapparatus. For instance, the control signal may send a request that thespeaker output a particular predefined audio signal to mask any noisesfrom the environment within an audio signal that may be subsequentlygenerated by the microphone.

Although the subject matter has been described in language specific tostructural features, it is to be understood that the subject matterdefined in the appended claims is not necessarily limited to thespecific features described. Rather, the specific features are disclosedas illustrative forms of implementing the claims.

What is claimed is:
 1. An apparatus comprising: a camera to generatevideo data representing an environment; a lens cap configured to cover alens of the camera; an actuator to move the lens cap between an openposition in the which the lens cap does not cover the lens and a closedposition in which the lens cap covers the lens; a physical control torequest to move the lens cap from the open position to the closedposition; a personal area network (PAN) component to enablecommunications compliant with at least one of the following standardsIEEE 802.15.4 (ZigBee), IEEE 802.15.1 (Bluetooth) or IEEE 802.11 (WiFi);one or more processors; and one or more non-transitory computer-readablemedia storing computer-executable instructions that, when executed onthe one or more processors, cause the one or more processors to performacts comprising: receiving, via the PAN component, a signal from anelectronic device that is separate from the apparatus, the signalcomprising an indication to move the lens cap from the closed positionto the open position; determining that the signal was received via thePAN component; and causing the actuator to move the lens cap from theclosed position to the open position based at least in part on thedetermining that the signal was received via the PAN component.
 2. Theapparatus as recited in claim 1, further comprising a wide area network(WAN) component to enable communications with devices over one or moreWAN, and wherein the signal comprises a first signal, the electronicdevice comprises a first electronic device, and the acts furthercomprise: receiving, via the WAN component, a second signal from asecond electronic device that is separate from the apparatus, the secondsignal comprising another indication to move the lens cap from theclosed position to the open position; determining that the second signalwas received via the WAN component; and sending, to the secondelectronic device and based at least in part on the determining that thesecond signal was received via the WAN component, a third indicationthat the lens cap will not be moved from the closed position to the openposition.
 3. The apparatus as recited in claim 1, further comprising awide area network (WAN) component to enable communications with devicesover one or more WAN, and wherein the signal comprises a first signal,the electronic device comprises a first electronic device, and the actsfurther comprise: receiving, via the WAN component, a second signal froma second electronic device that is separate from the apparatus, thesecond signal comprising another indication to move the lens cap fromthe closed position to the open position; receiving authenticationinformation from the second electronic device; and causing the actuatorto move the lens cap from the closed position to the open position. 4.The apparatus as recited in claim 1, wherein the apparatus and a mobiledevice are associated with a common user account, and the acts furthercomprise: receiving an indication that the actuator encountered aforeign object and is unable to move the lens cap from the at least oneof the closed position to the open position or from the open position tothe closed position; and sending at least one image generated by thecamera to the mobile device.
 5. The apparatus as recited in claim 1,further comprising: a microphone to generate an audio signal based onsound captured from the environment; and a speaker, proximate to themicrophone, to generate white noise; and the acts further comprising:receiving data indicating to mute the microphone; and causing thespeaker to generate the white noise to obfuscate at least a portion ofsound from the environment present in the audio signal.
 6. An apparatuscomprising: a camera; an obfuscation component to at least partlyobfuscate a view of the camera; a physical control to request to atleast partially obfuscate the view of the camera; a personal areanetwork (PAN) component to enable communications compliant with at leastone of the following standards IEEE 802.15.4 (ZigBee), IEEE 802.15.1(Bluetooth) or IEEE 802.11 (WiFi); one or more processors; and one ormore non-transitory computer-readable media storing computer-executableinstructions that, when executed on the one or more processors, causethe one or more processors to perform acts comprising: receiving, viathe PAN component, from a device, an indication to cease obfuscation ofthe view of the camera; determining that the indication was received viathe PAN component; and causing the obfuscation component to ceaseobfuscation of the view of the camera based at least in part on thedetermining that the indication was received via the PAN component. 7.The apparatus as recited in claim 6, wherein the acts further comprise:receiving, via the physical control, a second indication to at leastpartially obfuscate a view of the camera; and causing the obfuscationcomponent to at least partly obfuscate the view of the camera.
 8. Theapparatus as recited in claim 6, further comprising a wide area network(WAN) component to enable communications with devices over one or moreWAN, and wherein the device comprises a first device and the actsfurther comprise: receiving, via the WAN component, from a seconddevice, a second indication to cease obfuscation of the view of thecamera; and sending, to the second device, an indication that theobfuscation component will not cease obfuscation of the view of thecamera.
 9. The apparatus as recited in claim 6, wherein the obfuscationcomponent comprises: a lens cap configured to physically cover a lens ofthe camera; and an actuator configured to move the lens cap between afirst position physically covering the lens of the camera and a secondposition in which the lens cap does not physically cover the lens of thecamera.
 10. The apparatus as recited in claim 6, wherein the obfuscationcomponent comprises a light-source configured to emit lightsubstantially parallel to an optical axis of the camera, thelight-source configured to turn on to at least partially obfuscate theview of the camera and turn off to cease obfuscation of the view of thecamera.
 11. The apparatus as recited in claim 6, wherein the obfuscationcomponent comprises: a light-source configured to emit light; and alightguide at least partially within the camera to disseminate the lightfrom the light source to at least partially obfuscate the view of thecamera.
 12. The apparatus as recited in claim 6, wherein the apparatusand a mobile device are associated with a common user account and theacts further comprise: receiving another indication that the obfuscationcomponent is unable to at least partly obfuscate the view of the camera;and sending at least one image generated by the camera to the mobiledevice.
 13. The apparatus as recited in claim 6, further comprising: amicrophone to generate an audio signal based on sound from anenvironment of the apparatus; and a speaker, proximate to themicrophone; and the acts further comprising: receiving a secondindication to mute the microphone; and causing the speaker to generatenoise to obfuscate at least a portion of the sound from the environmentof the apparatus.
 14. A method implemented at least in part by anapparatus that includes a camera, an obfuscation component to at leastpartly obfuscate a view of the camera, a personal area network (PAN)component to communicate with a device over a PAN, and a physicalcontrol to request to at least partially obfuscate the view of thecamera, the method comprising: receiving, via the PAN component, fromthe device, an indication to cease obfuscation of the view of thecamera; determining that the indication was received via the PANcomponent; and causing the obfuscation component to cease obfuscation ofthe view of the camera at least partly in response to the determiningthat the indication was received via the PAN component.
 15. The methodas recited in claim 14, wherein the request comprises a first request,the device comprises a first device, and further comprising: receiving,via a wireless area network (WAN) component, from the second device, asecond indication to cease obfuscation of the of the view of the camera;sending, to the second device, data that the obfuscation component willnot cease obfuscation of the view of the camera; receiving, via the WANcomponent, from the second device, a third indication to receive videogenerated by the camera; and sending, via the WAN component, to thesecond device, the video generated by the camera.
 16. The method asrecited in claim 14, wherein the device comprises a first device, andfurther comprising: receiving, via a wireless area network (WAN)component, from a second device, a second indication to ceaseobfuscation of the view of the camera; sending, to the second device,data that the obfuscation component will not cease obfuscation of theview of the camera.
 17. The method as recited in claim 14, wherein theobfuscation component comprises a lens cap configured to physicallycover a lens of the camera, and wherein the causing comprises sending aninstruction to an actuator coupled to the lens cap to move the lens capto a position in which the lens cap at least partially obfuscate theview of the camera.
 18. The method as recited in claim 14, wherein theobfuscation component comprises a light-source configured to emit lightsubstantially parallel to an optical axis of the camera, and wherein thecausing comprises sending an instruction to the light-source to emit thelight substantially parallel to the optical axis of the camera to atleast partially obfuscate the view of the camera.
 19. The method asrecited in claim 14, wherein the obfuscation component comprises alight-source configured to emit light and a lightguide at leastpartially within the camera to disseminate the light from the lightsource to at least partially obfuscate the view of the camera, andwherein the causing comprises sending an instruction to the light-sourceto emit the light for dissemination by the lightguide.
 20. The method asrecited in claim 14, wherein the apparatus and a mobile device areassociated with a common user account, and further comprising: receivingdata that the obfuscation component is unable to at least partlyobfuscate the view of the camera; and sending at least one imagegenerated by the camera to the mobile device.